home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Almathera Ten Pack 3: CDPD 3
/
Almathera Ten on Ten - Disc 3: CDPD3.iso
/
scope
/
051-075
/
scopedisk71
/
syslog
/
syslog.doc
< prev
next >
Wrap
Text File
|
1995-03-19
|
11KB
|
330 lines
1
July 5, 1989 SysLog V1.4 - Amiga System Log Program
Overview
--------
SysLog provides a system logging function that can be common
to all aspects of your Amiga system. It simply appends a
timestamped, user-supplied comment to the SYSTEM.LOG, an
ascii text file located in the S: directory. Thus, the
S:SYSTEM.LOG can collect any information you wish to record,
keeping entries in chronological order and making them
easily available for subsequent searching, editing or
archiving. SysLog may be executed from the Workbench or the
CLI. It may be used from an Execute script to record the
execution or progress of your scripts or used in "requester"
mode to request log information from a user. If SYSTEM.LOG
is not already in your S: directory, it will be created the
first time you log a message.
Written by
----------
Don Nafis
Nazlo Associates Ltd.
P.O. Box 1515
Laurel Springs, NJ 08021
(609) 228-8088 Voice
(609) 227-8278 BBS -
Viva! Amiga!
3/12/24 - 8/N/1 - 24 hours
130 Megabytes
Compuserve 70656, 133
Copyright 1989, by Don Nafis & Nazlo Associates Ltd. All rights
reserved. May be copied and freely distributed for personal use.
If you find SysLog useful and you wish to contribute to future
versions, send your suggestions to one of the above.
If you wish to be a registered user, send $5.00 to the mailing
address above. This will help defray the expense of sending you
the next version of SysLog if, in fact, I do produce another
version.
Copyright 1989 by Don Nafis and Nazlo Associates Ltd. All rights reserved.
2
July 5, 1989 SysLog V1.4 - Amiga System Log Program
Usage
-----
From the CLI:
SysLog [ [-r[ user prompt]] | [message to log] ]
In its simplest form, SysLog appends the characters following
"SysLog" on the command line to a date and time stamp and appends
the resulting text string to the file S:SYSTEM.LOG. No quotes
are needed to contain the message; if quotes are used, they will
be logged with the message.
Examples:
SysLog System startup from BOOT:
SysLog Check out BBS. Viva! Amiga! (609)227-8278.
SysLog Jan had her baby. Named Michael - 8lbs 2oz.
SysLog Finished Version 1.4 of the SysLog program.
The format "SysLog -r" will pop a window on the screen requesting
"Make System Log Entry:". You can begin typing the message
immediately. If you mouse click anywhere else, the requester
will be de-selected so you will have to re-select it to enter
your message. When your message is complete, type <return> and
the message will be appended to S:SYSTEM.LOG. If you type
<return> without entering any text, the program terminates
without making an entry in S:SYSTEM.LOG. You may use normal
Intuition string editing features when typing your text entry.
The format "SysLog -r user prompt" (note the space between the
-r and the user prompt) will operate the same as SysLog -r but
place up to 50 characters of the text following "-r" into the
requester border to prompt for text entry. This form can be
useful if you wish to customize log information requests in
EXECUTE scripts.
Examples:
SysLog -r
SysLog -r Enter the latest news!
SysLog -r What is the weather like today?
Note that the message format and the -r format are mutually
exclusive.
Copyright 1989 by Don Nafis and Nazlo Associates Ltd. All rights reserved.
3
July 5, 1989 SysLog V1.4 - Amiga System Log Program
From the Workbench:
To execute from the Workbench, click on the SysLog icon. To make
it available, copy the files SysLog and SysLog.INFO to the drawer
you wish to use when you execute it.
Execution from the Workbench operates the same as the simple
"SysLog -r" format. You may not change the requester prompt as
you can from the CLI.
Some suggestions
----------------
Of course, you can log any event you care to, any comments that
you suspect may be interesting to review at some later time, but
these suggestions should give you some ideas.
-Place a syslog command in your startup-sequence to record when
you boot up and which startup-sequence or floppy you use to boot.
-Create a shutdown sequence to log the time that you quit, also
include the "Park" command for your hard disk if your hard disk
needs one. Thus you can record how much time you are spending on
your system each day. A good log of computer usage could help
substantiate a business expense claim on your income tax.
- Log a description or the progress of your more important
Execute scripts as they are executing. For instance, I boot
Viva! Amiga! from an Execute script, determining in the script if
the recovery program needs to be run. If so, the recovery script
is executed automatically. By logging both the startup and
recovery, I can capture a history of BBS problems.
- Keep a record of steps you take in developing a program. Make
an entry on those days you make major progress or those days when
you feel stumped.
- Log little tidbits of useless information when you really have
no place else to save them. A joke you heard, a phone number you
may never need but for some reason feel you must save, an
unforgettable quote that you may forget, the first time you heard
that the product you want to buy will be available "real soon
now", each time you hear it will be available "real soon now".
- Make a record of phone calls; on customer service type calls,
record who you called, why, who you talked to and what they said
they would do next. Use multiple entries if you need to record a
lot of information.
Copyright 1989 by Don Nafis and Nazlo Associates Ltd. All rights reserved.
4
July 5, 1989 SysLog V1.4 - Amiga System Log Program
- Log your system anomalies such as a disk read error, a program
GURU (after you re-boot). You can analyze the data over a period
of time to determine if things are getting worse, better or if
there is no pattern to any of your problems.
- Log the installation of all new software. This information may
be very useful if combined with system anomaly information.
By keeping all of this information in one place, in S:SYSTEM.LOG,
you will have no need to search through stacks of disks or papers
or scan hundreds of files looking for a piece of information you
knew you had recorded at some time in the past.
As you add more and more information to the SYSTEM.LOG, it could
grow pretty large. Each month, using an editor, I remove all
items logged for the previous month, create a separate file with
just these log entries, and ARC it into my running archive. In
this way, I can maintain a complete "diary" of system usage,
problems etc., without cluttering up my S: directory.
Sample Log Entries
------------------
June 23, 1989 08:28:47 System startup from BOOT:
June 23, 1989 19:06:29 Check out BBS. Viva! Amiga! (609) 227-8278.
June 23, 1989 20:10:30 Jan had her baby. Named Michael - 8lbs 2oz.
June 23, 1989 21:03:39 System shutdown.
June 24, 1989 11:53:02 System startup from BOOT:
June 24, 1989 12:10:06 The A2000 has arrived.
June 24, 1989 18:22:16 Finished Version 1.4 of the SysLog program.
June 24, 1989 19:02:51 System shutdown.
The Future of SysLog
--------------------
The following items are in the job jar for future versions of
SysLog:
- Residency. If enough people use SysLog enough of the
time, I may be convinced to make the code PURE so that it
may be used in resident mode. Assuming that multiple copies
could then be executing at the same time -
- Background execution. This means that one copy would be
running while additional invocations would pass the log
message to the background version for logging through a
message port. If this gets rolled in, the next logical step
Copyright 1989 by Don Nafis and Nazlo Associates Ltd. All rights reserved.
5
July 5, 1989 SysLog V1.4 - Amiga System Log Program
is -
- ARexx support. SysLog would be a resident ARexx host
process.
I'm not convinced that there is any advantage to ARexx
support though. Considering the following comparison:
Current use of SysLog in an ARexx script -
command 'syslog this will be logged in S:SYSTEM.LOG'
- or -
command 'syslog -r Enter something here:'
With SysLog as an ARexx host -
address 'SYSLOG'
'LOG this will be logged in S:SYSTEM.LOG'
- or -
address 'SYSLOG'
'REQUEST Enter something here:'
it seems like a toss-up. If I'm missing something, I'd
appreciate someone letting me know.
Copyright 1989 by Don Nafis and Nazlo Associates Ltd. All rights reserved.